Hi,
What is the recommended way to create a snapshot of (parts of) the DOORS database to install on a separate server for testing purposes?
I've tried working with partitions, but all the solutions I've found so far either
-
lock out the people on the production server (creating a R/W partition), or
-
prevent the developers on the test server from modifying the imported partition data.
The solution must be usable by end users, i.e. they do not have access to the machine running the DOORS server other than through the DOORS client.
Any and all hints/help appreciated.
SystemAdmin - Mon Jun 29 05:54:55 EDT 2009 |
|
Re: Recommended method of creating testing snapshots?
mcnairk - Mon Jun 29 08:14:57 EDT 2009
You don't say whether you need to merge the data modified on the test server back into the production server at some time in the future.
|
|
Re: Recommended method of creating testing snapshots?
SystemAdmin - Mon Jun 29 08:34:45 EDT 2009 mcnairk - Mon Jun 29 08:14:57 EDT 2009
You don't say whether you need to merge the data modified on the test server back into the production server at some time in the future.
|
|
Re: Recommended method of creating testing snapshots?
mcnairk - Mon Jun 29 09:19:26 EDT 2009 SystemAdmin - Mon Jun 29 08:34:45 EDT 2009
Sorry about that. To answer your question: The data transfer is assumed to be strictly one-way: from the production environment to the test environment.
Ken.
|
|
Re: Recommended method of creating testing snapshots?
SystemAdmin - Mon Jun 29 09:46:19 EDT 2009 mcnairk - Mon Jun 29 09:19:26 EDT 2009
Maybe I am missing something, but why not archive the project on your production server, restore it on your test server, then delete or make read-only the parts you don't want updated. Ensure that you set the Message of the Day to warn users that any changes they make to the test database will be lost.
Ken.
You're not missing anything at all. I, on the other hand, have learned something new today. Thanks!
|
|
Re: Recommended method of creating testing snapshots?
llandale - Mon Jun 29 12:51:01 EDT 2009
You could get your IT folks to backup the entire production database and install it on the test; then you purge the projects etc you don't want. This is the best way as it preserves the User database and all the access rights; correctly making the Test an accurate snap shot of the Production. Of course, anything that was in the Test would be lost.
You can archive individual projects and move them over.
You can create a Parition and move that like you did, and in the Production database you would 'Recover' the partition right after sending it thus freeing up the Production modules. Once you import the partion in the Test database, you can likewise tell the database to ignore the partion permanently freeing it up in the Test, I just don't recall how to do that.
|
|
Re: Recommended method of creating testing snapshots?
IBM_Gust - Tue Jun 30 07:58:37 EDT 2009 llandale - Mon Jun 29 12:51:01 EDT 2009
You could get your IT folks to backup the entire production database and install it on the test; then you purge the projects etc you don't want. This is the best way as it preserves the User database and all the access rights; correctly making the Test an accurate snap shot of the Production. Of course, anything that was in the Test would be lost.
You can archive individual projects and move them over.
You can create a Parition and move that like you did, and in the Production database you would 'Recover' the partition right after sending it thus freeing up the Production modules. Once you import the partion in the Test database, you can likewise tell the database to ignore the partion permanently freeing it up in the Test, I just don't recall how to do that.
|
|